All instructions have different performance, so If you need to time something it's best to unroll the operation rather than jam in within a tight loop. So your timing more of the operation and less loop overhead.
Time.Start = Timer()
For Count = 0 To CountMax
myTypeValue.AnInteger = 1
myTypeValue.AnInteger = 2
myTypeValue.AnInteger = 3
myTypeValue.AnInteger = 4
myTypeValue.AnInteger = 5
myTypeValue.AnInteger = 6
myTypeValue.AnInteger = 8
myTypeValue.AnInteger = 9
myTypeValue.AnInteger = 10
Next
Time.Stop = Timer()
Time.Duration = (Time.Stop - Time.Start) * 1000.0
Global Typed As Float : Typed = Time.Duration
Time.Start = Timer()
For Count = 0 To CountMax
myValue = 1
myValue = 2
myValue = 3
myValue = 4
myValue = 5
myValue = 6
myValue = 7
myValue = 8
myValue = 9
myValue = 10
Next
Time.Stop = Timer()
also, since reading is more prevalent than writing it's handy to time the read performance also.
Time.Start = Timer()
For Count = 0 To CountMax
temp =myTypeValue.AnInteger
temp =myTypeValue.AnInteger
temp =myTypeValue.AnInteger
temp =myTypeValue.AnInteger
temp =myTypeValue.AnInteger
temp =myTypeValue.AnInteger
temp =myTypeValue.AnInteger
temp =myTypeValue.AnInteger
temp =myTypeValue.AnInteger
temp =myTypeValue.AnInteger
Next
Time.Stop = Timer()
Time.Duration = (Time.Stop - Time.Start) * 1000.0
Global Typed As Float : Typed = Time.Duration
Most gains from runtimes/VM are found in caching results that tend to be consistently computed on demand..
etc etc