@jpihl This is an excellent check in the constructor! It does not sacrifice performance for correctness.
However, the granularity unit tests set the granularity dynamically after the stack is constructed, e.g. optimized.set_granularity(m_granularity);
Maybe set_granularity() is not needed in the unit test if we have the helper_region_info<0,0,16,16>???