Classes that want to 器具／実施する a 言及／関連-counting 機械装置 based on the
acquire()/解放（する）() interface should derive from this class.
The 推論する／理由 to have class 地元の 操作者s new and 削除する here is technical.
Imagine a class D derived from SimpleReferenceObject, but 器具／実施するd in
another 株d library that happens to use different 全世界の 操作者s new
and 削除する from those used in this 株d library (which, sadly, seems to
be possible with 株d libraries). Now, without the class 地元の
操作者s new and 削除する here, a code sequence like "new D" would use the
全世界の 操作者 new as 設立する in the other 株d library, while the code
sequence "削除する this" in 解放（する）() would use the 全世界の 操作者 削除する
as 設立する in this 株d library---and these two 操作者s would not be
保証（人）d to match.
There are no 積みすぎる 操作者s new and 削除する for placement new here,
because it is felt that the 概念 of placement new does not work 井戸／弁護士席
with the 概念 of 言及／関連-counted 反対するs; so it seems best to 簡単に
leave those 操作者s out.
The same problem as with 操作者s new and 削除する would also be there with
操作者s new[] and 削除する[]. But since arrays of 言及／関連-counted
反対するs are of no use, anyway, it seems best to 簡単に 宣言する and not
define (私的な) 操作者s new[] and 削除する[].
