title: What works in viewDidUnload should be moved to didReceiveMemoryWarning?
body: <p>In new iOS 6, <code>viewDidUnload</code> is deprecated and we have been instructed to use <code>didReceiveMemoryWarning</code> instead, to manage objects in UIViewController instances and subclasses. Is it equally effective to assign nils to UIView kinds inside <code>didReceiveMemoryWarning</code> like the way it has been done inside <code>viewDidUnload</code>?</p>
  
  <p>I am asking this because these two methods seems to be working differently. It seems like <code>didReceiveMemoryWarning</code> doesn't guarantee <code>viewDidLoad</code> to be called again to re-instantiate any necessary UIViews.</p>
  
  <p>I suspect with iOS 6, memory management is done without requiring to manually deallocate UIView. Please help me to know what I have missed in understanding the lifecycle of UIViewController. </p>