Peak values can be very useful in analyzing memory footprint. For example, want to know how much memory the compiler needs during warmup? You have to get an NMT report at the exact time - when the compile arena is at its largest extension. But if we had peak values, you'd see how much the compiler needed by looking at its peak extension.

We already collect peak values in debug builds, but never actually display them. Since we already pay for them, we might just as well print them.

There is also a small issue that peak size and count are updated separately. It makes not much sense to treat these as independent values. Therefore I propose to change the meaning and implementation of peak count from today's "highest count" to "count at the point peak size was reached".