The technical response to this thread:
The best way to measure the framerate is Mipey's method, and it is also already described on the wiki
because it's very common. There is no system expression to retrieve it, but it is trivial to set up the events.
The correct way to get the instantaneous
framerate - which is how many ticks would run in a second if every tick ran as fast as the last single tick did - is 1 / TimeDelta. However, this does vary a lot. The timer is almost perfectly accurate - it is correctly measuring fairly large variations in TimeDelta, which happens for various reasons (eg. the combination of Window's process scheduling and Vsyncing meaning occasionally a Vsync is missed and TimeDelta being around double the normal value). This does tend to make the displayed value unreadable though, because it varies so much. This is why I would prefer the previous method.
Cheez, you are on your way to a temp ban with your attitude, and you've been like this before. I feel your original "Don't tell me they forgot to add that in" and "should have existed from the very start" is belittling as if we are too stupid to think of putting that in, especially since you could have simply phrased it as "how about adding it if it isn't already there?" like most other forum members do. The rest of your posts have a generally bad and unhelpful attitude. Some people have responded badly but I think you are responsible for winding up, so please chill out and don't make me need to log in to the admin control panel in future.
I am satisfied my response completely answers the original question so to cool things off I'm closing the thread.