Removal of overwritten writes currently encompasses all the cases of the identical write removal.
Identical write removal might still be superior when partial writes (in preparation) do not share exactly the same domain, but can be merged into a single write. However, this could be implemented with overwritten write removal as well.
The identical write removal algorithm could be extended to handle all cases of overwritten removal, but with O(n^3) performance characteristic.
There is an observable behavioral change in that the last, instead of the first, MemoryAccess is kept. This should not affect the generated code, however.