The way I do it is very much like Option 3 above. However, I don't actually move actions onto NA lists because my software task tracker (the web-based SimpleGTD) just lets me "star" actions to make them show up as NAs. Keeping full action lists for each project makes it very easy to review my progress weekly.

However, you'll need to determine a GTD implementation that works for you. I recommend picking the method that seems best to you and just using it initially, tweaking things as you go. I took me quite a while to end up with a stable system; now that I have something that works for me, all of GTD just melts away into doing actual work.

Don't forget to separate your NAs by context, not by project. Creating your personal set of contexts is another very tricky thing, but again that's part of the process of developing your own GTD-based system. The key is just to pick something and start doing it without worrying whether it will be initially perfect (because it won't, no matter what). Refinements will come later, but you can't refine a process you haven't already started using!