Have you tried running the app using MemProof? It can be really
useful for determining where memory leaks are coming from - and
whether they are really leaks or just peculiarities in the operation.

I think the link is: http://www.automatedqa.com/index.asp but could
not get a response right now. Otherwise search the net for MemProof.

Geoff Worboys
Telesis Computing