Thanks for your answer. Because our code contains about 1000 source files I can't give you a code example. Instead I have uploaded on the following adress 8 print screens where you can see a part of the code where the memory leak apears and the Output window
with what the detector reports. I posted 2 examples for 2 Errors taken with the 1.9h and 2.0 version with StackWack set to fast and safe.
In the first example you can see the line of code whicah I add to generate the memory leak in the upper part of the picture
wchar_t *lpwszTestMemoryLeak = new wchar_t[MAX_PATH];
The only problem with this error apears in version 2.0 with fast mode because there is no CallStack reported.
In the second example the problems apears in version 2.0 with fast and safe mode. In fast mode we see that the CallStack is reported on the same location and all the leaks are merged in one.
In the safe mode we will notice that a function name CitireMuchiiAnotherVolume is not recognized and in 1.9h in both fast safe everyting it's Ok.
We are working with Visual Studio 2005 SP1 and this pictures where taken from a machine with Windows 7, but we also found the problems on Vista machine. I didn't test them on an XP machine.