It actually works the other way around, a result has to be "stored"
before it can be passed.  In either case, its *not* an optimization
worth worrying about in your code.

The truth is that you should use the second form because it has less
interaction with the surrounding context.  If you use:
long id = something;
then "id" is now part of your context.  Also, if someone gets the great
idea to reuse id, then it becomes harder to maintain down the road,
because you have to stop and think if which value of "id" are you
looking at.

In other words, when practical you should inline local variables to get
a more "functional programming" approach.  If you reuse a lengthy
calculation, you might then save it in a *final* declared variable then
(and only if a profiler tells you that you should).

To answer your original question, don't bother looking. Chances are its
not going to make a significant change to your programs speed.

Oh, and "long" isn't an object, its a primitive value.