Newer versions of DUnit optionally connect to FastMM4 and check for memory leaks after each test. This is visible in the graphical interface as a menu item.
Since DUnit is open source, I think this feature can also be used in a command line test (TextTestrunner).
In addition, DUnit can return the exit code if the tests do not work, so Finalbuilder should only check the exit code:
TextTestRunner.RunRegisteredTests(rxbHaltOnFailures);