Resolve "you are registering twice the same counter address" warning on Windows Release builds.
When registering profile counters on optimized Windows build you will get the following logging twice:
"you are registering twice the same counter address"
This happens since the optimizer will collapse cpu_load_1min, cpu_load_5min and cpu_load15min into
the same function on optimized Windows builds and that is not expected by register_internal.
By preventing inlining of cpu_load we can keep the different callback methods unique and optimizer
won't fold them into one single representation in the final binary.