Hilscher objects in the vendor specific range colliding with vendor specific user objects

Customer has legacy software where he uses vendor-specific object ids that are also used by the V3/V5 stack. Find & implement a mechanism to remove such collisions

Final design:

When the host registers a vendor-specific object (EIP_OBJECT_MR_REGISTER_REQ) which causes a conflict with a builtin Hilscher-specific object with the same class ID, then the registration will succeed anyway. Subsequently, the host-registered object will be adressed for explicit services over the network, instead of the Hilscher object. Thus, the Hilscher object will not be available to network peers anymore.
Anyway, at the DPM packet interface, the Hilscher-specific object will still be addressable, i.e. it still exists, concurrently using the same class ID, and the distinction between both is achieved by taking the interface into account as a secondary key to make the addressing unique.