>>39
On common C compilers for x86:
You do know that that doesn't measure much, except for your CPU's speed and if it's compiled to 32bit or 64bit code. Most compilers will allocate an entire register's size for a variable. So you end up with a stackallocated char/short/int taking a whole int for 32bit archs. For long long's, they'll use either 2 registers or one 64bit register if it was targetted for x86_64. Also note that various delays can be introduced because of context switches and other tasks running too.
If you really want to find out if something really matters, just fire up your favorite disassembler or have your C compiler generate an ASM listing, and the listing will explain why you got those numbers.