GetComponent performance profile in 2017 LTS

I see my getcomponent allocate like crazy and suck up cpu so I ran tests.
done with trios of getcomponent thingy over 500 instances

getcomponent<>().v1=1f or float c1=getcomponent<>().v1:
1 trio


10 trios

var c1=getcomponent<>() however…

so yeah
GetComponent<Stuff>().someVariable = thingy
is far better than

c.someVariable =trhingy

and the scene for fact checking

5913002–631526–tester of getcomponent.unitypackage (9.15 KB)

This is possible, but I imagine with things like IL2CPP the difference will narrow, or could even reverse if there were clever compiler tricks involved.