we only support process monitoring, so enforce that in the API
we don't really support demonitor/2, so rip it out
due to the aggregration of all monitors of a single pid into a single
monitor, the semantics of demonitor/2 is decidely dodgy
cosmetics, better var names, and optimise 'DOWN' sending