Bullshit. Making an OS 64 bit is far more complex than a recompile. And the next Android version, Kit-Kat is not expected to be 64 bit compatible.
That is true, porting objective-c code from 32 to 64 bits is tricky, and that is why Apple is doing it now. In the future when apple does need more than 4 GB of RAM in their devices, they will need to have apps that can take advantage of that. They are making 64 bit available very early so apps will be ready by then.
64 bit gives more registers and some bigger floating point operations, which marginally benefits some apps (it is not ground breaking). But the real advantage of 64 bit is the ability to address more than 4 GB of RAM, which is moot in the iPhone 5c and 5s since they only have 2 GB. So this is more about laying the foundation for future devices/apps than actually benefiting users of 5c and 5s.
Android 64 bit is at least a year away.
Sure, but the situation is very different. You see, most android Apps are not compiled to ARM. They are compiled to Dalvik, which has a bytecode that does not care if it runs in 32 bit or 64 bit. What this means is that at some point, when Google makes Dalvik 64 bit, the vast majority of the apps that run in Android will automatically be 64 bit, without even recompiling.
So unlike with iOS, Google can take its time and do the switch when it is actually useful.