Dunno about that, Nick. So far as I'm concerned, anything that installs and/or updates using NT SERVICE\TrustedInstaller involves a very large element of user trust in the product. And that's without even considering the creation of tasks that run as NT AUTHORITY\SYSTEM. In any case, my saying that I took it "on trust" in Macrium's case was intended as complimentary and definitely not otherwise. I'm certainly not doubting your word, nor Mike's, on the subject.
Yes, I see now that v7 got the same treatment. Guess I missed that release having gone back to v6 for now. I still wonder, however, if the same treatment was enough for v7 with its additional auto-start services and the switch to the task scheduler v2.0 API. Seems to me its services might require greater access to more than just Reflect's own registry keys to determine, for example, notification preferences, background task handling, etc., especially when running under W10 and all its various updates. As I said, just a thought. Most definitely not intended to complicate Mike's efforts. Trying to decipher Microsoft's ambiguous information is sufficiently difficult without my dubious "help".
Regards, Richard V. ("Arvy")