IIUC, the optimization indicates the ordinal that was changed; it doesn't indicate which value was deleted. You would have to look at the previous revisions to to find out which value got deleted.

This is just an observation. I'm not sure if it indicates a problem.

Would introducing the optimization cause any complication with existing data? In other words, could Envers deal with both optimized and non-optimized collection audit tables?