While investigating the performance issue with the `available()` function in the allocator, the arithmetic of range type resources, namely ports, appear to be most expensive. And the subtraction proves to be significantly more expensive than the addition whose cause is not immediately clear to me.
While we do have a benchmark `Resources_Scalar_Arithmetic_BENCHMARK_Test` that contains a range parametrized test, its result is somewhat misleading. It evaluates the addition performance by repeatedly summing up the same port resources which is fine. However, when evaluating the subtraction, it took the result from the addition and repeatedly subtracting the same port resources. The result is that after the first subtraction, the subtrahend becomes empty and all the subsequent subtractions are shorthanded, producing uninstructive result.