Look at the new test. If you multiply the allocation rate from `gc.alloc.rate.norm` by the benchmark throughput, it would disagree with `gc.alloc.rate`. This is because `gc.alloc.rate` is computed by GC profiler using its own timer, which accidentally includes the artificial delay before deregistering the GC notifications.