Be draconian about using readonly where appropriate
Have different default PropertyChanged and CollectionChanged despatchers

This is because PropertyChanged events can be async - WPF handles the
marshalling. However if CollectionChanged events are async, then the
thing listening to the event can still be iterating the collection while
the user's editing it, leading to irritating little exceptions