Memory Profiler under-reports ALLOC_TEMP_JOB_ASYNC footprint, causing unused blocks to appear as Untracked

Steps to reproduce:

1. Do a heavy burst of concurrent Addressables load operations.
2. Take a capture in the Memory Profiler and watch Native/Reserved/ALLOC_TEMP_JOB_ASYNC spike.
3. Wait a few minutes.
4. Take another capture.

Actual results: 

In the second capture (after waiting), Native/Reserved/ALLOC_TEMP_JOB_ASYNC has gone back to a lower memory footprint. At the same time, `Untracked/Private` has increased by roughly the same amount of memory.

Expected results: 

Native/Reserved/ALLOC_TEMP_JOB_ASYNC is a grow-only allocator. It cannot shrink, and thus it is expected for the memory profiler to show an unchanged or increased memory footprint. The `Untracked/Private` region should not have grown.

Reproducible with versions: Unity 6000.3.9f1, Memory Profiler 1.1.9

Not reproducible with versions: 

Can’t test with versions: 

Tested on (OS): WinEditor, MacEditor, Android, iOS

Notes: