What are the memory requirements of EV3-G software blocks running on NXT bricks? The NXT brick has about 130K memory available for user programs.

With the newer firmware required for downloading EV3-G programs that memory has been reduced to 118K.

How much memory is used by the various blocks available in EV3-G?

What tricks can be used to cram many programs onto the NXT brick's limited memory space?

I'm a coach of an FLL team that is using the NXT brick.  Should they use EV3-G or stick with NXT-G?

See Comparison of 10 blocks shows memory usage of NXT-G and EV3-G are nearly identical.
The move steer and move tank blocks take 5kb each while the large motor block takes 4kb. If you have a long string of move blocks in your program, it will take up big chunks of memory. We've gotten around that in the past with using myblocks. Myblocks are only copied to the NXT once and called each time it is needed in the program. A pivot myblock might take 7kb but you can use it as many times as you like without taking up more memory. We make a myblock for just about every common move used in our programs. It pays to make a myblock if a string of code will be used more than once.

I would stick with EV3 software if you plan to move to the EV3 hardware in the next season or two. I personally liked NXT-g better but we upgraded our hardware to EV3 this year.

Edit - I just compared the NXT blocks to the EV3 blocks and there is quite a difference. The NXT-g move block only takes 2.4KB and the motor block takes 1.1KB. Our pivot myblock that takes 7KB in EV3 only takes 1.6KB in NXT.