Dependancies in Ansistring handling.

Maybe it's a good idea to keep a similar file (non ASCII-art, the second part) in the project.

Pascal:

Incr_Ansi_Ref looks lonely, doesn't it? It isn't used. Where necessary
it's inlined.

Marked with a * are non-Astring routines


    /--------------------------AssignAnsiString--------\
   |                                                   |
   |   UniqueAnsiString    /------------------------------------ SetLength
   |       |        \      |                           |           |
    \      V         ------------->--------------------|---\  /----/
     \                     |                           |   V  |
      Decr_Ansi_Ref ----<--/    Incr_Ansi_Ref       NewAnsiString
           |                                               |
           V                                               V
    DisposeAnsiString                                  *GetMem
           |
           V
        *freemem


A bit more readable: (the number before the name is the number of the procedure,
    the numbers after it, the procedures it calls.
    sequences (1-2-3) mean that 1 calls 2 which calls 3 etc.

0 Length
1 FreeMem
2 GetMem
3 DisposeAnsiString  1
4 Decr_Ansi_ref      3-1
5 UniqueAnsiString   4-3-1
6 NewAnsiString      2
7 AssignAnsiString   4-3-1   6-2
8 SetLength          4-3-1   6-2      0
9 Copy               0       10
10 *Move


Assembler:
--------

Same as Pascal, Move, Length and Copy will be inlined in the assembler
procedures, maybe sometimes decr_ref to (in some procedures the reference-count
has been checked, and is >1 1 or -1. The corresponding part of decr_ref could
be inlined. This however is a future target, when the library is stable, and
not changing day to day )

