An Environment Browser open on an RBModel, e.g. to browse the content of
a deployed application, throws DNUs when attempting to browse references
to instance variables, protocols, and method categories.

Following recent changes to image deployment COM functions required by
implementations of COM interfaces are being removed, with this breaking
deployment of the Simple Web Browser example. This is because the
defineFunctions methods are now being removed. The function tables need to
be considered as sources of message sends, except where the interface is
for egress only, i.e. unless only used for call out. By default all
interfaces are considered potentially implementable, with an opt-in flag
to mark those known to be egress only.

- In some cases newer interfaces being removed as classes unreferenced, so
downcast not finding them. This results in some functionality not working,
e.g. profiles.
- Event handlers/completion handlers may require structure or interface
argument types that were being removed as the interface functions were
ungenerated.
- The majority of the large number of interfaces are egress-only, so can
be marked as such to reduce the size of the deployed application.

- XMLDOM - mostly, excluding SAX handlers
- VBScript regex - all