.NET Continuous Profiler: Memory Usage

In the fourth part of this series on Datadog's .NET profiler, memory usage profiling is covered. This feature allows users to identify when their application causes high CPU consumption due to excessive garbage collection by the runtime. It also helps pinpoint which parts of the code are responsible for the most memory allocation and view a sample of objects that stay in memory after garbage collection. The implementation includes monitoring garbage collector activity, tracking allocations, and surviving objects. Memory leaks in .NET can be hard to find due to false positives, but by keeping track of each live object's age, it becomes possible to discern between a refreshed cache and a real memory leak. Upscaling issues are also discussed, as the current implementation does not upscale sampled values for allocations and live objects.