'Repeated property access of built in component is inefficient' for Property setters is pointless

[Santifocus]

In this context there is no point in showing this warning, due to how Unity handles CharacterControllers (and NavMeshAgents) positions they need to be disabled before changing their position and then re-enabled afterwards meaning this is perfectly valid code but Rider assumes some inefficiency here.