This is something I've always been unsure on. Since the module *uses* the UAVO, this protects against weird resets when the UAVO owner for some reason fails to initialize the UAVO. This can arise while refactoring a the owner module. My personal preference would be that a module should initialize every UAVO that it uses.

@solidgoldbomb Can you do a comparison/contrast with the situation where only the UAVO's owner initializes it?