constructor TCustomIniFile.Create(const FileName: string);

constructor TCustomIniFile.Create(const FileName: string);
begin
  FFileName := FileName;
end;

Been looking for a memory problem for a couple days. On a lark, I ran PAL to help find stuff. It pointed out Create() methods that didn't call "inherited" in the constructor. 

However, it found a couple in the XE2 source
System.Inifiles.TCustomIniFile.Create()
and 
System.Win.Registry.TRegistry.Create() and the overloaded version and the fancy class constructor

I was under the impression that one must pretty much always call inherited first, but then I saw this...

http://www.delphibasics.co.uk/RTL.asp?Name=Inherited

"It is called at the start of a constructor, and at the end of a desctructor. It is not mandatory, but recommended as good practice."

Ctrl-Click on inherited Create() for an Object, sure seems to have code that should go first (in all cases?).

So I guess I'm kind of confused on when inherited is NOT something you'd call each and every time and what happens if you don't...