Fix#723: Memory: active allocations are incorrectly displayed in call stack tree
The range we were looking for was wrong (should be Active instead of
Inactive), but I also reworked to make the comparison clearer.
Test
Using the repro app from the bug:
1. Click "Free + Allocate" once
1. Call stack tree shows 2 entries under "Active allocations", 1 active
allocation, 0 inactive allocations in the call stack tree.
1. Click "Free + Allocate" several times
1. Call stack tree shows 1 KB of active allocations and many KB of
inactive.
