title: sonarLint complains "Null pointers should not be dereferenced (squid:S2259)" despite that possibility being handled
body: <p>So I have an issue with SonarLint that I am not sure how to approach.</p>
  
  <p>let's say I have a class with a method </p>
  
  <pre><code>public class Class(RemoteContext context)
      RemoteContext context = context;
  
      public void String method(String data) {
          if(data == null)
              context.raiseException("data can't be null");
  
          //do stuff with data like data.get();
      }
  </code></pre>
  
  <p>When I analyze this class with sonarLint (3.2.) I get a  Null pointer should not be dereferenced issue.</p>
  
  <p>So my question is. How to solve this issue?
  <code>context.RaiseException</code> will stop method execution so I think it is a false positive.</p>
  
  <p>The application has a lot of cases (classes/methods) with this problem.
  So I'm thinking that annotations are an overkill (ugly code all around)
  I could also type return after each <code>raiseException()</code> call, but I'm under the impression that is not the "programmers way".</p>
  
  <p>I'm guessing writing my own rule would be best.</p>
  
  <p>I was looking over the topics and did me googling around but did not find anything useful for this case, when I sort of having to do the "opposite" of what sonar actually does. 
  Not raising an issue, but kind of "giving a green light" on the method?</p>
  
  <p>Hopefully, I was clear enough on the issue.</p>