It seems odd to write a fuzz target to trigger integer sanitizer warnings in CBlockPolicyEstimator::processBlockTx
and then suppress them. If the scenario can happen in reality, the code should be properly fixed to handle the cases. If not, it seems better to fix the fuzz target to not trigger meaningless traces.
Do that here by keeping track of the current height and limiting mempool entries to at most this entry height.