This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
We have a strict policy on display names, which must be a real first and last name with a space between. No last initials, please.
Please go here and fix your display name up, pronto. Thanks, pardner!
Now, as to your question: micro-optimizations like this never make any sense in Java. What's faster on one JVM may be slower on another. More importantly, the HotSpot JVM looks for specific patterns in your bytecode and knows how to optimize them in a platform-specific way; if you use unusual coding idioms, like backwards loops, you may stop HotSpot (or another optimizing JVM or JIT) from doing its job.
So not only should you not do this, you should not even worry about little things like this -- in general, you'll only manage to slow things down by writing tricky code. Write clear, readable code, and trust the JVM to make it fast.