Borland C++ 3.1, 4.5: Recently this has been my main development platform, so naturally everything works with this compiler. There was a problem with the library utility in version 2.0 which is now fixed. You will need to use the large model. If you are not debugging, turn off the options that collect debugging information. Make sure you don't run Borland's exceptions and my simulated exceptions at the same time.
When running my test program with Borland 4.5 under ms-dos you may run out of memory. Either compile the test routine to run under easywin or use simulated exceptions rather than the built in exceptions. Under easywin the test program indicates a memory leak. I presume this is partly because of the way windows organises its heap rather than there being a real problem.
However there does seem to be genuine memory problem when you use the built-in exceptions. Under easywin the automatic clean-up of objects by the exception mechanism does not seem to work. Use my simulated exceptions if this is a problem.