title: iOS: Creating an ABNewPersonViewController under ARC gives "Potential leak" warning
body: <p>EDIT: Sorry for my question. It turned out that the error was in the line before the one that was flagged by the static analyzer.<br>
  In this line, I called a <strong>Obj-C method</strong> that creates and returns an <code>ABRecordRef</code>, and although I balanced the creation of the CF object by a <code>CFRelease</code> in the calling code, the static analyzer was apparently not sure if the memory management of the CF object was done correctly, thus the "potential leak".<br>
  I converted the method to a <strong>C function</strong>, and the warning is gone.</p>
  
  <p>ORIGINAL QUESTION:<br>
  Under ARC, I have a subclass of a <code>UINavigationController</code> that is presented modally.<br>
  In the <code>viewDidLoad</code> method, I set up an <code>ABNewPersonViewController</code>, and present it by pushing it onto the navigation stack, using the following code:  </p>
  
  <pre><code>ABNewPersonViewController *personViewController = [[ABNewPersonViewController alloc] initWithNibName:nil bundle:nil];
  personViewController.newPersonViewDelegate = self;
  personViewController.displayedPerson = self.contactToBeAdded;f
  [self pushViewController:personViewController animated:NO];  
  </code></pre>
  
  <p>Everything works fine, but the static analyzer gives, at the 1st line of the code,  the warning "<strong>Memory (Core Foundation/Objective-C) Potential leak of an object</strong>".<br>
  I don't understand why there is this warning, and how I could get rid of it.<br>
  Any suggestion?</p>