title: UITableViewController ignores tap after deleting row in iOS7
body: <p>Consider the following plain and simple <code>UITableViewController</code>: when you tap a row, it logs the selected row, and when you swipe and delete, it removes an item in the model and reloads the data.</p>
  
  <pre><code>@interface DummyTableViewController : UITableViewController
  
  @property (nonatomic, strong) NSMutableArray *items;
  
  @end
  
  @implementation DummyTableViewController
  
  - (instancetype)initWithStyle:(UITableViewStyle)style
  {
      self = [super initWithStyle:style];
      if (self)
      {
          _items = [ @[ @"A", @"B", @"C", @"D", @"E" ] mutableCopy];
      }
      return self;
  }
  
  - (NSInteger)numberOfSectionsInTableView:(UITableView *)tableView
  {
      return 1;
  }
  
  - (NSInteger)tableView:(UITableView *)tableView numberOfRowsInSection:(NSInteger)section
  {
      return [self.items count];
  }
  
  - (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath
  {
      UITableViewCell *cell = [[UITableViewCell alloc] initWithStyle:UITableViewCellStyleSubtitle reuseIdentifier:nil];
      cell.textLabel.text = self.items[indexPath.row];
      return cell;
  }
  
  - (void)tableView:(UITableView *)tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath *)indexPath
  {
      if (editingStyle == UITableViewCellEditingStyleDelete)
      {
          [self.items removeObjectAtIndex:indexPath.row];
          [tableView reloadData];
      }
  }
  
  - (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath
  {
      NSLog(@"Row %@ tapped.", self.items[indexPath.row]);
  }
  </code></pre>
  
  <p>In iOS6, this all works as expected, but in iOS7 I get the following behavior: <em>after a row has been removed and the data has been reloaded, the first next tap on a table cell is ignored</em>. It is only the second tap that triggers a table cell select again. Any idea what might be causing this or how to work around it? Issue should be easy to reproduce in iOS7 with the above code.</p>