Resources object can be mutated through the public API

The Resources object current allows mutation of it's internal state through the public mutable iterator interface.
This can cause issues when the mutation involved stripping certain qualifiers on a Resource, as they will not be summed together at the end of the mutation (even though they should be).

The contains() math will not work correctly if two addable resources are not summed together on the lhs of the contains check.