When we select a tombstone in reconciliation, we append an update to the update list representing the on-disk value. Since it is in the in-memory update list, it needs to be taken into account as part of our cache usage calculation.

We're not suffering any ill effects from this. I just noticed it when scanning through the reconciliation code.