What is the best way to find memory leaks in CW 3.0, without having the S60 source code or symbols? The emulator displays an ALLOC message at closing time, so what can one do about it?

All my old methods do not work anymore:

- note memory region from ALLOC message
- conditional breakpoint on ALLOC, look for register EAX value of address
- rerun App
- triggers on all allocs with wanted address

CW 2.5:
- note memory region from ALLOC message
- set memory watch on the region
- rerun app
- it breaks on all allocs with same address

Could CW not just record all alloc addresses and matching source code line numbers of a thread, so in case of a panic, one could search the list of allocs with the same address? There are gigabytes of memory lying around anyway...