This is a kind of follow-up from bug 1600. I've removed Object.prototype from the prototype chain of the global object and re-ran the test suite. The following tests did not complete successfully:
Most of the time this happens because `hasOwnProperty()` or `propertyIsEnumerable` is called on the global object. But without `Object.prototype` being present in the global object's proto-chain, trying to call these functions fails at runtime.
Applying the obvious workarounds should fix these problems, that means using something like `Object.prototype.hasOwnProperty.call(globalObject, 'property-name')`.