There's only one way to deal with leaks: Find them and fix them.
Leaks don't necessarily come from new/malloc statements in your own code, they could also happen indirectly if you don't call the proper cleanup methods in library code.
There are two methods to find leaks:
- Use a static analyzer that examines logical errors in your code.
- Run the executable using a memory profiler and watch for unreleased resources.
With good tools tiny leaks should be as easy to detect as massive ones.