Does Player variable leak?

Basically when i am using a for-loop to cycle through players, and call Player(i) at every iteration, do i create leaking handles?

If it indeed leaks, then if i make it like this:

Will the leak go away?

Setting variables to null doesn't destroy the object they point to; however, it's still neccesary with local handle variables, even if the object they point to is destroyed, they must be set to null at end of function. But that's a different kind of leak.

As for players, they are handles, but not dynamically created. When using the Player() function (or any other that returns a player), it doesn't create a new object, but use one that is created when the map starts.

Whew....
Half of my triggers use for-loops for player cycling. If it leaked, it would be a MAJOR pain to rewrite :)

I have a furhter question on the same topic
Suppose there is a function, which takes Player as an argument, and i don't initialise a special variable to pass it over to this function, but rather simply do:

The function itself looks like:

Do i need to set plr to null at the end of this function, so there are no leaks?

Or do i need to go something like this at the function call:

Actually Cubasis figured out a long ago that the bug with local handle variables leaking doesn't happen with arguments