🚀 go-pugleaf

I am plagued with VCL and cp3240mt.dll memory leaks using C++ Builder
v3.0.  My application runs in the tooltray and so is always present,
consuming copious amounts of memory over time. Looking at the task
manager under NT shows that my app is the biggest kid (or pig) on the
block!

I've used BoundsChecker, MemProof, and Memory Sleuth to the point
where the only leaks remaining are the Borland DLLs.

I've slugged my way through hundreds of news messages regarding this
issue only to come to the conclusion that the Borland v3.0 DLLs leak
and there isn't much to be done about it!

One suggestion was to build w/o packages, another to not use the RTL
libraries, neither which is doable in my situatuion as I have too many
DLLs and EXEs in my project. Using static libraries would bloat my
entire project to the point of being unusable or undesirable.

Soooo.....my question is whether I should upgrade to C++ Builder 4.0
in the hope of having some of the memory leak issues resolved. Does
anyone have experience with leaks having been, or not, resolved by
taking the upgrade path?

Thanks for any feedback.
-Bill