EMF monitor error due to dependent features

[HeikoKlare]

If features implicitly depend on each other, the EMF monitor produces false results.
This is, for example, the case when using UML: The value of the contract feature of an
InterfaceImplementation is also represented in the supplier feature and automatically added to that feature. So one change description for setting the contract and one for adding the supplier are generated by our monitor. When rolling them back, the supplier is first removed by the second change description, which results in an also removed contract (due to their dependency). When rolling back the second change description for the contract, nothing happens. Reversing this procedure results in a missing contract, because the change description lost the information as the supplier removal removed the contract as well

[HeikoKlare]

This issues is subsumed by #489.