The "standard"/obvious usecase is broken.

This is more of a question than an issue with the code.

If use the plugin to add a `SetRotationExecuting` event to `Transform` and then add a handler to a transform, the following happens:

1. `transform.rotation = Random.rotation;` causes the handler to be called.
2. `transform.Rotate(Random.insideUnitSphere);` does **not** cause the handler to be called.

Does this mean that I need to monitor the whole chain of `localRotation`s and `parent`s instead of just the one `rotation` I am interested in?

This would require a bit of quite gnarly code and I am not sure that I am not missing something else I would also need to monitor.

Did you solve this problem in your [Unity.TransformChangesDebugger.API](https://github.com/handzlikchris/Unity.TransformChangesDebugger.API)?