I know that there's a lot on what with the 64-bit version, keeping pace with visual studio, fixing bugs, coping with whatever Microsoft throws up in terms of changes to Windows, and all the rest of it, so I am completely understanding about priorities and all that. I also understand that printing documentation is an expensive overhead. I had a look at the costs of small runs of properly bound booklets and my goodness, aren't they expensive.
When I look at the online documentation (and by that I include web, the help file, the PDFs of old documents and the enhancements file) I know that if there is something that I know already exists, that I might have used but don't really remember the details, then if I'm prepared to put in the time and effort I can find it. Well mostly. I'm also someone who has taken the time to read the documentation in advance of having specific needs in my programs. But I'll never be able to find something that simply isn't there!
The help documentation isn't always very searchable, it is often not complete, and it definitely doesn't often list some of the deficiencies or limitations. As to the 5000 separate choices, I'm glad I'm not running that particular bit of software. But it might have been useful to point out in the documentation that the list was limited to 64K characters. Perhaps yet another file on this site or in the distribution listing known limitations and 'issues' could be at least in part an answer.
Eddie