Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

(This is kind of a continuation of bug 148441, which
was closed prematurely.)

valgrind+wine can indeed already spot leaks in programs
that call the win32 heap directly, but not in programs
which use a higher level heap (e.g. tcmalloc,
jemalloc, hoard, nedmalloc, etc).

To fix this properly, we need to port valgrind.h to win32 
so that client requests can be made from win32 apps. 
The attached demo that shows this works from win32 apps
compiled with gcc, so fixing valgrind.h for that case
shouldn't be hard at all.
Supporting Visual C++ is a bit harder, since its inline
assembly is different.  (The demo tries to support that, 
but I made a mistake somewhere.)