Back in 1988, \count19 was used in Plain TeX for storing the most recently allocated \insert.
In the current Plain TeX (and also in LaTeX) the counter to be used is \count20, because \count19 keeps track of languages.
Here's an excerpt of latex.ltx (line 302 onwards)
\message{registers,}
\count10=22 % allocates \count registers 23, 24, ...
\count11=9 % allocates \dimen registers 10, 11, ...
\count12=9 % allocates \skip registers 10, 11, ...
\count13=9 % allocates \muskip registers 10, 11, ...
\count14=9 % allocates \box registers 10, 11, ...
\count15=9 % allocates \toks registers 10, 11, ...
\count16=-1 % allocates input streams 0, 1, ...
\count17=-1 % allocates output streams 0, 1, ...
\count18=3 % allocates math families 4, 5, ...
\count19=0 % allocates \language codes 1, 2, ...
\count20=255 % allocates insertions 254, 253, ...
\countdef\insc@unt=20
\countdef\allocationnumber=21
As far as the extended pool is concerned, you should have a look at the macros provided by etex.sty:
\documentclass{article}
\usepackage{etex}
\newcount\myalloc
\def\tryalloc{%
\begingroup
\loop\ifnum\myalloc<350
\advance\myalloc 1
\expandafter\loccount\csname tempcount\romannumeral\myalloc\endcsname
\expandafter\locdimen\csname tempdimen\romannumeral\myalloc\endcsname
\expandafter\loctoks\csname temptoks\romannumeral\myalloc\endcsname
\expandafter\meaning\csname tempcount\romannumeral\myalloc\endcsname\par
\expandafter\meaning\csname tempdimen\romannumeral\myalloc\endcsname\par
\expandafter\meaning\csname temptoks\romannumeral\myalloc\endcsname\par
\repeat
\endgroup
\vskip 40pt
\expandafter\meaning\csname tempcount\romannumeral350\endcsname}
\begin{document}
\ttfamily\tryalloc
\end{document}
You'll see that \loc... allocates registers from the top (32767) downwards, and that after the group the meaning is forgotten.
These commands are briefly discussed in etex_src.html that should be available with texdoc etex_src. The file etex.sty is essentially a verbatim port to LaTeX of etex.src.
etex.styfor many years, but not used widely. We did try providing local allocation inexpl3, but it did not really fit well with how TeX works (as you still need to track the scope groups rather than of functions): it was removed some time ago. So I'd say that while local allocation is possibly, it's not a good 'fit' for how TeX programming works, especially as e-TeX gives us lots of registers. – Joseph Wright♦ Jun 4 '12 at 8:05